Add dietary requirements + buildup/teardown registration to the volunteer system #1821
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lukegb
force-pushed
the
buildup-teardown-reg
branch
2 times, most recently
from
1b76485 to
7925d21
Compare
Contributor
|
No specific requirements. I'd hope that the list of people with nonempty requirements is short enough that we can manually process it; adding specific requirements is likely to cause trouble. The one thing we could do is split dietaries and allergies, and make it clear what we consider the difference to be:
Let me take this to the team, we have a meeting next week. |
Member
Contributor
|
Discussed with the team. Proposed form: Allergies (will cause health issues if ingested):
Dietary Restrictions:
|
There's no admin UI for this yet to actually export the aggregate stats for the kitchen. Closes #1746.
The general expected flow is this: * Someone generates a team token in volunteering admin * URLs make their way into people's hands * Users sign up - this can be with or without an account via a ticket * Users enter the information required for a volunteering account, as well as their expected arrival/departure date/time, and an emergency contact, and ack the Safety on Site briefing * Once they arrive, they scan a QR code that takes them to the "I'm arrived" site - this records their arrival timestamp and gives them a link to the Signal group chat and shows them the Safety on Site briefing again Note that, at present: * There's no way to un-volunteer. You can set your arrival/departure dates to just be "normal" times, though, I suppose, and/or never actually show up. * We don't show the team that you're associated with anywhere except the admin page, and it's set based on the link you used to register. * There's no export of this data yet. Closes #1797.
lukegb
force-pushed
the
buildup-teardown-reg
branch
from
7925d21 to
a7d0620
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| return response | ||
|
|
||
| # They completed registration: | ||
| return redirect(get_next_url(default=url_for(".buildup_amend"))) |
Check warning
Code scanning / CodeQL
URL redirection from remote source Medium
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dietary requirements
This is bare-minimum - just a plain-text field in the volunteer profile. There's no export yet. @paullessing probably has some requirements here that might be useful for more structured data?
Buildup/teardown registration
There are three entrypoints:
All of these show the Safety on Site text. Maybe we could put this somewhere else for all except the "arrived on site" page.